Monitoring and capturing early diagnostic data

ABSTRACT

A deviance monitoring module is provided for examining various parameters of an operating system for deviance from a baseline behavior at specified intervals. A range of acceptable deviance values from a baseline behavior is set for parameters of an operating system. The parameters of the operating system are then monitored at specified intervals for deviance from the baseline behavior. In response to detecting that the deviance exceeds a predetermined threshold, the method triggers diagnostic data gathering on the parameters of the operating system according to an embodiment.

DOMESTIC PRIORITY

This application is a continuation of the legally related U.S.application Ser. No. 13/747,928 filed Jan. 23, 2013, which is fullyincorporated herein by reference.

BACKGROUND

The present invention relates to computer systems management, and morespecifically, to monitoring parameters of an operating system fordeviance from a baseline behavior and to triggering diagnostic datagathering in response to the deviance exceeding a predeterminedthreshold.

When contemporary operating systems experience an error or unexpectedresult in a computing environment, a great deal of time and resourcesare typically spent determining the root cause of the error orunexpected result. Typically, insufficient documentation is collected onthe operating systems to allow a complete diagnosis to be performed.Clients and testers are required to recreate error situations to attemptto gather additional documentation on a subsequent failure. By the timea software problem percolates up to the operating system, making itselfknown, the initial problem may have already disappeared from traces,making the debugging of the initial problem difficult.

SUMMARY

According to an embodiment, a computer-implemented method that isimplemented by a processing device is provided for setting a range ofacceptable deviance values from a baseline behavior for parameters of anoperating system. The parameters of the operating system are thenmonitored at specified intervals for deviance from the baselinebehavior. In response to detecting that the deviance exceeds apredetermined threshold, the method triggers diagnostic data gatheringon the parameters of the operating system according to an embodiment.

According to another embodiment, a computer system including aprocessor, a system memory, and a bus that couples various systemcomponents including the system memory to the processor, is configuredto set a range of acceptable deviance values from a baseline behaviorfor parameters of an operating system. The parameters of the operatingsystem are then monitored at specified intervals for deviance from thebaseline behavior. In response to detecting that the deviance exceeds apredetermined threshold, the computer system triggers diagnostic datagathering on the parameters of the operating system according to anembodiment.

According to another embodiment, a computer program product including anon-transitory computer readable storage medium having computer readableprogram code stored thereon that, when executed, provides the setting ofa range of acceptable deviance values from a baseline behavior forparameters of an operating system. The parameters of the operatingsystem are then monitored at specified intervals for deviance from thebaseline behavior. In response to detecting that the deviance exceeds apredetermined threshold, the computer readable program code triggersdiagnostic data gathering on the parameters of the operating systemaccording to an embodiment.

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention. For a better understanding of the invention with theadvantages and the features, refer to the description and to thedrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter which is regarded as the invention is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The forgoing and other features, and advantages ofthe invention are apparent from the following detailed description takenin conjunction with the accompanying drawings in which:

FIG. 1 depicts a block diagram of a computer system according to anembodiment; and

FIG. 2 depicts a flow diagram of a monitoring operation for monitoringan operating system or program for deviance from a baseline behavioraccording to an embodiment.

DETAILED DESCRIPTION

Embodiments disclosed herein provide the monitoring of parameters of anoperating system for deviance from a baseline behavior and thetriggering of diagnostic data gathering in response to the devianceexceeding a predetermined threshold.

In the contemporary art, clients and testers typically attempt todetermine an apparent root cause of the problem by setting a trap ofsome sort for a particular condition, and then attempting to recreatethe problem, if possible, to catch earlier data. This typically requiresmultiple iterations, and assumes that the problem can be easilyrecreated, which is often not true.

Embodiments disclosed herein provide a deviance monitoring module forexamining various parameters of an operating system for deviance from abaseline behavior at specified intervals. In response to the devianceexceeding a specified threshold, a diagnostic gathering module istriggered to automatically gather diagnostic data documentation.Accordingly, the diagnostic data documentation is potentially gatheredearly enough in the life cycle so that the root of the problematicparameter may be debugged quickly without the need for multiplerecreates. Further, in response to the deviance values of a monitoredparameter returning to a specified value within the time frame specifiedon an exception list, the diagnostic data documentation will be loggedand deleted after a specified period of time according to embodiments.Any time the diagnostic gathering module gathers diagnosticdocumentation, a notification may alert an interested parties list.Embodiments also provide the initiation of recovery or remediationactions.

Referring now to FIG. 1, a block diagram of a computer system 10suitable for monitoring parameters of an operating system for deviancefrom a baseline behavior and triggering diagnostic data gathering inresponse to the deviance exceeding a predetermined threshold. Computersystem 10 is only one example of a computer system and is not intendedto suggest any limitation as to the scope of use or functionality ofembodiments described herein. Regardless, computer system 10 is capableof being implemented and/or performing any of the functionality setforth hereinabove.

Computer system 10 is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with computer system 10include, but are not limited to, personal computer systems, servercomputer systems, thin clients, thick clients, cellular telephones,handheld or laptop devices, multiprocessor systems, microprocessor-basedsystems, set top boxes, programmable consumer electronics, network PCs,minicomputer systems, mainframe computer systems, and distributed cloudcomputing environments that include any of the above systems or devices,and the like.

Computer system 10 may be described in the general context of computersystem-executable instructions, such as program modules, being executedby the computer system 10. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system 10 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules may be located inboth local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system 10 is shown in the form of ageneral-purpose computing device. The components of computer system mayinclude, but are not limited to, one or more processors or processingunits 16, a system memory 28, and a bus 18 that couples various systemcomponents including system memory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system 10 may include a variety of computer system readablemedia. Such media may be any available media that is accessible bycomputer system/server 10, and it includes both volatile andnon-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system 10 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the disclosure.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

According to an embodiment, a deviance monitoring module 100 carries outthe functions and/or methodology for monitoring parameters of anoperating system or a program for deviance from a range of acceptablevalues from a baseline behavior. The deviance monitoring module 100includes a diagnostic gathering module 102 for gathering diagnostic datafor each monitored parameter of the operating system or program, and anexception list 104 including a set of parameters and their allowableamount and time of deviation from a baseline behavior.

Computer system 10 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 10; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 10 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system 10 can communicate withone or more networks such as a local area network (LAN), a general widearea network (WAN), and/or a public network (e.g., the Internet) vianetwork adapter 20. As depicted, network adapter 20 communicates withthe other components of computer system 10 via bus 18. It should beunderstood that although not shown, other hardware and/or softwarecomponents could be used in conjunction with computer system 10.Examples include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID systems,tape drives, and data archival storage systems, etc.

With reference now to FIG. 2, a monitoring operation 200 for monitoringan operating system or program for deviance from a baseline behavior isshown in accordance with an embodiment.

In block 210, a deviance range of acceptable values is set in thedeviance monitoring module 100 for certain parameters of the operatingsystem or program. In an embodiment, a user may provide the expectedand/or allowed range of acceptable values for certain parameters of theoperating system to the deviance monitoring module 100. The range ofacceptable values may be set according to historical data observed by aseparate monitoring application according to an embodiment.

In block 220, the operating system is monitored at specified intervalsfor deviance from the range of acceptable values set in block 210 forcertain parameters of the operating system. According to an embodiment,a user may set the specific intervals for monitoring the deviance ofcertain operating system parameters. Depending on the operating systemor program being monitored, the data can be collected in a number ofknown ways. For example, an operating system may report data in systemmanagement facility (SMF) records and via resource management facility(RMF) interfaces, while other operating systems may provide applicationprogramming interfaces (APIs).

In block 230, the deviance monitoring module 100 determines whether amonitored parameter exceeds the predetermined range of acceptable valuesset in block 210 according to an embodiment. If the monitored parameterdoes not exceed the predetermined range of acceptable values, then thedeviance monitoring module 100 continues to monitor the operating systemparameters at the specified intervals as shown in block 220. If,however, the monitored parameter does exceed the predetermined range ofacceptable values, the diagnostic gathering module 102 is triggered anddiagnostic data is gathered on the monitored parameter as shown in block240. Along with the monitoring values, a set of diagnostic data to begathered for each monitored parameter may be provided by a user or aseparate monitoring application. The gathered diagnostic data may be inaddition to or instead of an optional default data diagnosticapplication of the computer system 10.

According to an embodiment, the deviance monitoring module may includean exception list 104 that includes a set of parameters and theirallowable amount and time of deviation from the baseline behavior.

For example, on a regular basis, a program that does databaseoptimization may run, and during that time, I/O rates and centralprocessing unit (CPU) utilization may increase. If there are allowedexceptions, the exception may consist of the affected monitoredparameter (in this case, there would be one entry for I/O rates and onefor CPU utilization), a list of programs/address spaces associated withthe changed to the monitored parameter (in this case, either thedatabase program or the optimization program), the amount of expecteddeviation to the parameter, a time value for the duration of clock timethat the associated program/address space(s) are allowed to cause theparameter to deviate from the expected value, and one or more sets ofpercentages of various time units that the program is expected to causethe parameter to deviate.

As an example, in the case of the database optimization program, assumethat the database optimization program is expected to run once a day,and that it is expected to run for half an hour when it runs. This meansthat the duration of clock time that the database optimization programwould be allowed to run without triggering the data gathering of anembodiment would be 50% of any given hour, and 2.1% of any given day.Accordingly, an embodiment handles the case where, for example, a bug istriggered that causes the CPU utilization by the database optimizationprogram to run for 15 minutes every hour. The 50% of any given hourcondition set in the exception list of an embodiment would be satisfied,but not the 2.1% utilization for any given day condition.

As shown in block 250, in response to a monitored parameter triggeringthe diagnostic gathering module 102, an embodiment determines whetherthe deviance falls within the exception list 104. The exception listspecifies an allowable time frame for monitored parameter values with adeviance exceeding a predetermined threshold to return within limits ofthe predetermined threshold.

In response to the deviance of the monitored parameter returning to apredetermined threshold within a specified amount of time specified inthe exception list, the diagnostic data is logged and deleted after apredetermined period of time, as shown in block 260. The deviancemonitoring module 100 then continues to monitor the operating systemparameters at the specified intervals as shown in block 220.

In response to the deviance of the monitored parameter not returning toa predetermined threshold within a specified amount of time specified inthe exception list, the deviance monitoring module 100 initiates a knownrecovery or remediation application, as shown in block 270. The deviancemonitoring module 100 then continues to monitor the operating systemparameters at the specified intervals as shown in block 220.

According to an embodiment, any time the diagnostic gathering module 102gathers diagnostic documentation, interested parties may be notified. Anotification may be transmitted via email, pager, SMS, and/or the liketo anyone on an interested parties' list based on the types of alertsthey are interested in.

An example of an implementation of an embodiment of the deviancemonitoring module 100 will now be discussed. On a z/OS system, ascheduler attempts to ensure that every running program has some amountof access to the CPU in accordance with the importance of the program.Programs of similar importance will generally have equal access to theCPU, assuming that they do not have to wait for I/O to complete. So aprogram that simply does addition, and is running at a high importance,should have frequent access to the CPU. A monitoring may be set up tolook in the scheduler control blocks to see the last time the programran, and compare that to the current time. If the difference betweenthose two times exceeded a given interval, data gathering could betriggered.

Other examples of implementation of embodiments of the deviancemonitoring module 100 may include memory usage, which might indicate astorage leak, I/O rates, log update rates, time inside a subroutine.Similarly, for some programs, CPU, memory access, and I/O activity arecorrelated, so a program that is expected to do frequent memory and I/Oaccess while it is using the CPU (e.g., the database optimizationprogram) could potentially be looping if it is only using the CPU for anextended period of time. Similarly, a task that primarily does I/Oshould be generating memory access requests and I/O requests, but if itbegins using large amounts of real memory itself it could be leakingmemory. For work that is transaction-oriented, either havingtransactions take significantly longer or shorter than a specifiedvalued could indicate a hang or a recursive failure.

Embodiments may have value on other platforms and hardware. Both storageand processor hardware have expected ranges they operate within, forsuch things as I/O rates, instructions per second, cache utilization,buffer sizes, and the like. Deviation from norms for a given customercould also be used to identify potential error situations and activate astate save or enhanced tracing for a period of time that would allowbetter diagnostics of factors leading up to a failure. Accordingly,embodiments also apply to other platforms and their associated hardware,both in the open systems areas as well as with portable and handhelddevices.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readablestorage medium. A computer readable storage medium may be, for example,but not limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, or device, or any suitablecombination of the foregoing. More specific examples (a non-exhaustivelist) of the computer readable storage medium would include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), an optical fiber, a portable compact disc read-onlymemory (CD-ROM), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The disclosed flowchart and block diagrams illustrate the architecture,functionality, and operation of possible implementations of systems,methods and computer program products according to various embodimentsof the present invention. In this regard, each block in the flowchart orblock diagrams may represent a module, segment, or portion of code,which comprises one or more executable instructions for implementing thespecified logical function(s). It should also be noted that, in somealternative implementations, the functions noted in the block may occurout of the order noted in the figures. For example, two blocks shown insuccession may, in fact, be executed substantially concurrently, or theblocks may sometimes be executed in the reverse order, depending uponthe functionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts, or combinations of special purpose hardware andcomputer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, element components,and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

The flow diagrams depicted herein are just one example. There may bemany variations to this diagram or the steps (or operations) describedtherein without departing from the spirit of the invention. Forinstance, the steps may be performed in a differing order or steps maybe added, deleted or modified. All of these variations are considered apart of the claimed invention.

While the preferred embodiment to the invention had been described, itwill be understood that those skilled in the art, both now and in thefuture, may make various improvements and enhancements which fall withinthe scope of the claims which follow. These claims should be construedto maintain the proper protection for the invention first described.

What is claimed is:
 1. A computer-implemented method, comprising:setting, with a processing device, a range of acceptable deviance valuesfrom a baseline behavior for parameters of an operating system, whereina user provides the range of acceptable deviance values from thebaseline behavior for parameters of the operating system; monitoring theparameters at specified intervals for a deviance from the baselinebehavior; determining whether the deviance falls within an exceptionlist, wherein the exception list specifies an allowable time frame formonitored parameter values with a deviance exceeding a predeterminedthreshold to return within limits of the predetermined threshold andwherein the exception list also specifies a list of programs associatedwith the monitored parameter values; triggering diagnostic datagathering on the parameters of the operating system in response to thedeviance exceeding the predetermined threshold; notifying interestedparties of the gathered diagnostic data; and initiatingrecovery/remediation actions in response to the deviance exceeding apredetermined threshold, wherein, in response to the deviance returningwithin a predetermined threshold within a specified amount of timespecified in the exception list, the diagnostic data is logged anddeleted after a predetermined period of time.